chore: npm-check-updates && yarn upgrade#36613
Conversation
Ran npm-check-updates and yarn upgrade to keep the `yarn.lock` file up-to-date.
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
@Mergifyio refresh |
✅ Pull request refreshed |
|
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
Merge Queue Status🚫 The pull request has left the queue (rule: This pull request spent 3 hours 36 minutes 43 seconds in the queue, with no time running CI. ReasonPull request #36613 has been dequeued. The pull request rule doesn't match anymore HintYou should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it. |
|
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
|
@Mergifyio requeue |
✅ This pull request will be embarked automaticallyDetailsThe head sha of this pull request, 7e48b0a, was never embarked in the merge queue. But don't worry, Mergify will embark it automatically for you. |
🛑 There are no queue conditions matchingDetailsThere are queue conditions defined in the configuration, but none matches. The pull request has not been embarked. Details:
|
Merge Queue Status🛑 Queue command has been cancelled |
|
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
|
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
Merge Queue Status✅ The pull request has been merged at aefd003 This pull request spent 22 hours 14 minutes 31 seconds in the queue, including 49 minutes 31 seconds running CI. Required conditions to merge
|
|
Comments on closed issues and PRs are hard for our team to see. |
Ran npm-check-updates and yarn upgrade to keep the
yarn.lockfile up-to-date.